home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20000217-20000824
/
000234_news@columbia.edu _Thu Apr 27 05:06:48 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@columbia.edu>
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
by fozimane.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id FAA23398
for <kermit.misc@cpunix.cc.columbia.edu>; Thu, 27 Apr 2000 05:06:47 -0400 (EDT)
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id FAA09731
for <kermit.misc@watsun.cc.columbia.edu>; Thu, 27 Apr 2000 05:06:46 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id EAA16083
for kermit.misc@watsun.cc.columbia.edu; Thu, 27 Apr 2000 04:57:33 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: Ishikawa <ishikawa@yk.rim.or.jp>
Subject: Re: Parity incorrectly reported, and RTS/CTS problem on Solaris 7 for
Date: Thu, 27 Apr 2000 17:46:05 +0900
Organization: RIMNET InterNetNews site
Message-ID: <3907FE4D.8FCDB4E8@yk.rim.or.jp>
To: kermit.misc@columbia.edu
Hello,
(Any volunteers yet?)
> : Here is my take on why this problem was not noticed before
> : by the many kermit users on Sun boxes, and if my guess is correct,
> : the problem didn't harm many people at all.
> :
> : - Hardware flow-control is only necessary when
> : CPU/OS is rather slow in comparison to the serial line speed.
> : Thanks to the deep hardware FIFO queue in serial controller, and
> : ever faster CPU...
> :
> Yes, that's true in one direction, but what about the other?
Forgot about the other direction!
>
> a. SVR4-style hardware flow control works in Solaris in one direction but
> not the other; or:
>
> b. Kermit's dynamic packet sizing got around the errors, so nobody noticed
> them; or:
>
> c. Nobody has been using > 57600 bps serial speeds; or:
>
> d. Nobody is reporting problems.
>
I would think that b, and c ("Bad cable" and shurrugedoff).
a is a little difficult, but anything goes with software.
>
> : If my reading of the messages is correct, solaris up to 2.3 did
> : set RTS/CTS using ATT SysV semantics.
> : The first broken version of kermit for Solaris 2.4 for x86
> : didn't suffer much since the OS itself doesn't seem to have
> : support for 115200 bps at all.
> :
> So you have determined that SVR4 hwfc works in Solaris 2.3 and earlier?
> I didn't see anything about this in yesterday's posting.
>
Sorry to confuse you. I `assume'd that
since nobody seemed to have reported problems on earlier systems
(2.3 and older) [and assumed that you picked up SVR4 hwfc for a
reason for solaris target] that SVR4 hwfc worked on such systems.
Can't verify since these are indeed old systems and
I have no way to test such systems.
>: PS: if we can return the failure code (-1) from
>: the att sysV semantics functions(s) to higher level
>: funtions, at least we can tell the user that something is woring by
>: printing some meaningful messages.
>:
> Yes, I can take of this. It will be in the next release. But it won't
> affect Solaris > 2.3, since this code won't be used there any more, right?
Quite right. -DPOSIX_CRTSCTS would take care of this.
Happy Hacking,
Ishikawa